Resumption of program or erase operations in memory

ABSTRACT

A system includes a memory component and a processing device, operatively coupled with the memory component, to send a read command to the memory component while a program or erase operation being executed by the memory component is suspended. The processing device, operatively coupled with the memory component, can then send an auto resume command to the memory component to automatically resume execution of the program or erase operation after the read command is executed.

TECHNICAL FIELD

Embodiments of the disclosure relate generally to memory sub-systems,and more specifically, relate to resumption of program or eraseoperations in memory.

BACKGROUND

A memory sub-system can include one or more memory devices that storedata. The memory devices can be, for example, non-volatile memorydevices and volatile memory devices. In general, a host system canutilize a memory sub-system to store data at the memory devices and toretrieve data from the memory devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be understood more fully from the detaileddescription given below and from the accompanying drawings of variousembodiments of the disclosure.

FIG. 1 illustrates an example computing system that includes a memorysub-system in accordance with some embodiments of the presentdisclosure.

FIG. 2 is a flow diagram of a process to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure.

FIG. 3 is a flow diagram of a process to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure.

FIG. 4 is a flow diagram of a process to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure.

FIG. 5 is a flow diagram of a process to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure.

FIG. 6 is a flow diagram of an example method to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure.

FIG. 7 is a block diagram of an example computer system in whichembodiments of the present disclosure can operate.

DETAILED DESCRIPTION

Aspects of the present disclosure are directed to resumption of programor erase operations in memory. A memory sub-system can be a storagesystem, storage device, a memory module, or a combination of such. Anexample of a memory sub-system is a storage system such as a solid-statedrive (SSD). Examples of storage devices and memory modules aredescribed below in conjunction with FIG. 1. In general, a host systemcan utilize a memory sub-system that includes one or more components,such as memory devices that store data. The host system can provide datato be stored at the memory sub-system and can request data to beretrieved from the memory sub-system.

A read command can be sent to, and executed by, a storage device of amemory sub-system while another memory operation (e.g., a program,erase, or other memory operation) being performed by the memory deviceis suspended. In a conventional memory sub-system, the read command canautomatically trigger a resumption of the other operation, causing adrain of page buffer resources in the memory sub-system. For example,the same page buffer resources used to resume the other memory operationcan also be used to execute the read command (e.g., to transfer the readdata), creating a conflict between executing the read command andexecuting the other memory operation. A memory sub-system traditionallymay not have the resources to support the resumption of the other memoryoperation concurrently with the read data transfer.

Aspects of the present disclosure address the above and otherdeficiencies by sending an auto resume command to the memory component(e.g., storage device) such that the other memory operation does notresume until an auto resume command is received and the read command isexecuted. A resume continuation command can also be sent after the readcommand has been executed, when page buffer resources are to be used.The resume continuation can resume the memory operation responsive towhether a checkpoint for resuming the memory operation has been met.

The auto resume command allows for the execution of read commands whilethe other memory operation is suspended and there are not enough pagebuffer resources to execute both the read command and the other memoryoperation. As such, issuing a read command will not automaticallytrigger a resumption of memory operations and as such, page bufferresources can be used more efficiently. The resume continuation commandalso allows for more effective use of page buffer resources because thepage buffer resources are not activated until used. In some embodiments,after the read command has been executed, the resume continuationcommand can pause the memory operation until a checkpoint is reached. Acheckpoint is triggered responsive to a request for page bufferresources. Therefore, page buffer resources are not used untilrequested.

FIG. 1 illustrates an example computing system 100 that includes amemory sub-system 110 in accordance with some embodiments of the presentdisclosure. The memory sub-system 110 can include media, such as one ormore volatile memory devices (e.g., memory device 140), one or morenon-volatile memory devices (e.g., memory device 130), or a combinationof such.

A memory sub-system 110 can be a storage device, a memory module, or ahybrid of a storage device and memory module. Examples of a storagedevice include a solid-state drive (SSD), a flash drive, a universalserial bus (USB) flash drive, an embedded Multi-Media Controller (eMMC)drive, a Universal Flash Storage (UFS) drive, a secure digital (SD)card, and a hard disk drive (HDD). Examples of memory modules include adual in-line memory module (DIMM), a small outline DIMM (SO-DIMM), andvarious types of non-volatile dual in-line memory modules (NVDIMMs). Thememory sub-system 110 can include one or more memory components thatstore data. The memory components can be, for example, non-volatilememory components and volatile memory components. In general, a hostsystem can utilize a memory sub-system 110 to store data at the memorycomponents and to retrieve data from the memory components.

The computing system 100 can be a computing device such as a desktopcomputer, laptop computer, server, network server, mobile device, avehicle (e.g., airplane, drone, train, automobile, or other conveyance),Internet of Things (IoT) enabled device, embedded computer (e.g., oneincluded in a vehicle, industrial equipment, or a networked commercialdevice), or such computing device that includes memory and a processingdevice.

The computing system 100 can include a host system 120 that is coupledto one or more memory sub-systems 110. In some embodiments, the hostsystem 120 is coupled to different types of memory sub-system 110. FIG.1 illustrates one example of a host system 120 coupled to one memorysub-system 110. As used herein, “coupled to” or “coupled with” generallyrefers to a connection between components, which can be an indirectcommunicative connection or direct communicative connection (e.g.,without intervening components), whether wired or wireless, includingconnections such as electrical, optical, magnetic, and the like.

The host system 120 can include a processor chipset and a software stackexecuted by the processor chipset. The processor chipset can include oneor more cores, one or more caches, a memory controller (e.g., an SSDcontroller), and a storage protocol controller (e.g., PCIe controller,SATA controller). The host system 120 uses the memory sub-system 110,for example, to write data to the memory sub-system 110 and read datafrom the memory sub-system 110.

The host system 120 can be coupled to the memory sub-system 110 via aphysical host interface. Examples of a physical host interface include,but are not limited to, a serial advanced technology attachment (SATA)interface, a peripheral component interconnect express (PCIe) interface,universal serial bus (USB) interface, Fibre Channel, Serial AttachedSCSI (SAS), Small Computer System Interface (SCSI), a double data rate(DDR) memory bus, a dual in-line memory module (DIMM) interface (e.g.,DIMM socket interface that supports Double Data Rate (DDR), Open NANDFlash Interface (ONFI), Double Data Rate (DDR), Low Power Double DataRate (LPDDR), or any other interface. The physical host interface can beused to transmit data between the host system 120 and the memorysub-system 110. The host system 120 can further utilize an NVM Express(NVMe) interface to access components (e.g., memory devices 130) whenthe memory sub-system 110 is coupled with the host system 120 by thePCIe interface. The physical host interface can provide an interface forpassing control, address, data, and other signals between the memorysub-system 110 and the host system 120. FIG. 1 illustrates a memorysub-system 110 as an example. In general, the host system 120 can accessmultiple memory sub-systems via a same communication connection,multiple separate communication connections, and/or a combination ofcommunication connections.

The memory devices 130, 140 can include any combination of the differenttypes of non-volatile memory devices and/or volatile memory devices. Thevolatile memory devices (e.g., memory device 140) can be, but are notlimited to, random access memory (RAM), such as dynamic random-accessmemory (DRAM) and synchronous dynamic random access memory (SDRAM).

An example of non-volatile memory devices (e.g., memory device 130)includes a negative-and (NAND) type flash memory. Each of the memorydevices 130 can include one or more arrays of memory cells. The memorycells can include single level cells (SLCs) that can store one bit percell, multi-level cells (MLCs) that can store two bits per cell, (e.g.,triple level cells (TLCs) that can store three bits per cell, quad-levelcells (QLCs) that can store four bits per cell, and/or penta-level cells(PLCs) that can store five bits per cell, among others. As used herein,the term multiple level cells is used to refer to cells configured tostore more than one bit per cell (e.g., MLC, TLC, QLC, PLC, etc.). Insome embodiments, a particular memory component can include an SLCportion, and an MLC portion, a TLC portion, a QLC portion, and/or a PLCportion of memory cells. Each of the memory cells can store one or morebits of data used by the host system 120. Furthermore, the memory cellsof the memory devices 130 can be grouped as memory pages or memoryblocks that can refer to a unit of the memory component used to storedata.

Although non-volatile memory components such as NAND type memory (e.g.,2D NAND, 3D NAND) are described, the memory device 130 can be based onany other type of non-volatile memory or storage device, such as,read-only memory (ROM), phase change memory (PCM), self-selectingmemory, other chalcogenide based memories, ferroelectric transistorrandom-access memory (FeTRAM), ferroelectric random access memory(FeRAM), magneto random access memory (MRAM), Spin Transfer Torque(STT)-MRAM, conductive bridging RAM (CBRAM), resistive random accessmemory (RRAM), oxide based RRAM (OxRAM), negative-or (NOR) flash memory,electrically erasable programmable read-only memory (EEPROM), and across-point array of non-volatile memory cells. A cross-point array ofnon-volatile memory can perform bit storage based on a change of bulkresistance, in conjunction with a stackable cross-gridded data accessarray. Additionally, in contrast to many flash-based memories,cross-point non-volatile memory can perform a write in-place operation,where a non-volatile memory cell can be programmed without thenon-volatile memory cell being previously erased.

The memory sub-system controller 115 (or controller 115 for simplicity)can communicate with the memory devices 130 to perform operations suchas reading data, writing data, or erasing data at the memory devices 130and other such operations. The memory sub-system controller 115 caninclude hardware such as one or more integrated circuits and/or discretecomponents, a buffer memory, or a combination thereof. The hardware caninclude digital circuitry with dedicated (i.e., hard-coded) logic toperform the operations described herein. The memory sub-systemcontroller 115 can be a microcontroller, special purpose logic circuitry(e.g., a field programmable gate array (FPGA), an application specificintegrated circuit (ASIC), etc.), or other suitable processor.

The memory sub-system controller 115 can include a processing device,which includes one or more processors (e.g., processor 117) configuredto execute instructions stored in a local memory 119. In the illustratedexample, the local memory 119 of the memory sub-system controller 115includes an embedded memory configured to store instructions forperforming various processes, operations, logic flows, and routines thatcontrol operation of the memory sub-system 110, including handlingcommunications between the memory sub-system 110 and the host system120.

In some embodiments, the local memory 119 can include memory registersstoring memory pointers, fetched data, etc. The local memory 119 canalso include read-only memory (ROM) for storing micro-code. While theexample memory sub-system 110 in FIG. 1 has been illustrated asincluding the memory sub-system controller 115, in another embodiment ofthe present disclosure, a memory sub-system 110 does not include amemory sub-system controller 115, and can instead rely upon externalcontrol (e.g., provided by an external host, or by a processor orcontroller separate from the memory sub-system).

In general, the memory sub-system controller 115 can receive commands oroperations from the host system 120 and can convert the commands oroperations into instructions or appropriate commands to achieve thedesired access to the memory device 130 and/or the memory device 140.The memory sub-system controller 115 can be responsible for otheroperations such as wear leveling operations, garbage collectionoperations, error detection and error-correcting code (ECC) operations,encryption operations, caching operations, and address translationsbetween a logical address (e.g., logical block address (LBA), namespace)and a physical address (e.g., physical block address, physical medialocations, etc.) that are associated with the memory devices 130. Thememory sub-system controller 115 can further include host interfacecircuitry to communicate with the host system 120 via the physical hostinterface. The host interface circuitry can convert the commandsreceived from the host system into command instructions to access thememory device 130 and/or the memory device 140 as well as convertresponses associated with the memory device 130 and/or the memory device140 into information for the host system 120.

The memory sub-system 110 can also include additional circuitry orcomponents that are not illustrated. In some embodiments, the memorysub-system 110 can include a cache or buffer (e.g., DRAM) and addresscircuitry (e.g., a row decoder and a column decoder) that can receive anaddress from the memory sub-system controller 115 and decode the addressto access the memory device 130 and/or the memory device 140.

In some embodiments, the memory device 130 includes local mediacontrollers 135 that operate in conjunction with memory sub-systemcontroller 115 to execute operations on one or more memory cells of thememory devices 130. An external controller (e.g., memory sub-systemcontroller 115) can externally manage the memory device 130 (e.g.,perform media management operations on the memory device 130). In someembodiments, a memory device 130 is a managed memory device, which is araw memory device combined with a local controller (e.g., localcontroller 135) for media management within the same memory devicepackage. An example of a managed memory device is a managed NAND (MNAND)device.

The memory sub-system 110 can include an auto resume component 113.Although not shown in FIG. 1 so as to not obfuscate the drawings, theauto resume component 113 can include various circuitry to facilitatecontinuing the suspension of memory operations (e.g., program or eraseoperations) unless an auto resume command is received by memory device130. For example, the execution of a read command sent to the memorydevice will not trigger a resumption of a suspended program or eraseoperation by memory device 130 unless an auto resume command has beenreceived by the memory device, as will be further described herein. Theauto resume component 113 can include a special purpose circuitry in theform of an ASIC, FPGA, state machine, and/or other logic circuitry thatcan allow the auto resume component 113 to orchestrate and/or performthe operations described herein.

The memory sub-system 110 can also include a resume continuationcomponent 116. Although not shown in FIG. 1 so as to not obfuscate thedrawings, the resume continuation component 116 can include variouscircuitry to facilitate confirming a resume continuation command hasbeen received by memory device 130. For example, the memory device 130can resume execution of a memory operation (e.g. a program or eraseoperation) responsive to receiving the resume continuation command priorto, or subsequent to, a checkpoint for resuming the operation being met,as will be further described herein. The checkpoint can correspond topage buffer resources being sought for execution of a memory operation.The resume continuation component 116 can include a special purposecircuitry in the form of an ASIC, FPGA, state machine, and/or otherlogic circuitry that can allow the resume continuation component 116 toorchestrate and/or perform the operations described herein.

In some embodiments, the memory sub-system controller 115 includes atleast a portion of the auto resume component 113 and the resumecontinuation component 116. For example, the memory sub-systemcontroller 115 can include a processor 117 (processing device)configured to execute instructions stored in local memory 119 forperforming the operations described herein. In some embodiments, theauto resume component 113 and the resume continuation component 116 arepart of the host system 110, an application, or an operating system

As an example, controller 115 can send a read command to memory device130 while a program or erase operation being executed by memory device130 is suspended, and auto resume component 113 can send an auto resumecommand to memory device 130 to automatically resume execution of theprogram or erase operation after the read command is executed. The autoresume command can be sent by auto resume component 113 before or afterthe read command is sent to memory device 130. For instance, the autoresume command can be sent any time during the execution of the readcommand. In one example where the auto resume command is sent to memorydevice 130 after the read command is sent to the memory device 130, thememory device 130 is given a longer period to execute the read commandthan an example where the auto resume command is sent to the memorydevice 130 before the read command. Execution of the suspended programor erase operation may only resume after execution of the read command,and the data read during execution of the read command can betransferred to controller 115 while the execution of the suspendedprogram or erase operation has resumed (e.g., concurrently with theexecution of the program or erase operation).

The resumption of the program or erase operation execution can betemporary. For example, the memory device 130 can confirm if a resumecontinuation command has been received from the resume continuationcomponent 116. The memory device 130 can resume (e.g., continueresumption of) execution of the program or erase operation responsive toconfirming that the resume continuation has been received and that acheckpoint for resuming the operation has been met. The checkpoint forresuming the operation can correspond to, for instance, an amount ofpage buffer resources being used by the memory device 130. The resumecontinuation command can be sent before or after the memory device 130has confirmed whether it has received the resume continuation command.For instance, the confirmation of the resume continuation command can beresponsive to page buffer resources being used by the memory device 130.In an example where the resume continuation command is sent after memorydevice 130 has confirmed the resume continuation command has beenreceived and the checkpoint for resuming the operation has not been met,the memory device 130 can pause execution of the program or eraseoperation. The paused program or erase operation can be resumedresponsive to receiving the resume continuation command.

During suspension of a program or erase operation, the memory device 130can ensure received read commands do not trigger a complete resumptionof the program or erase operation before confirming if a resumecontinuation command has been received. For example, memory device 130can temporarily resume execution of the program or erase operation afterthe auto resume command has been sent, while the data during executionof the read command is being transferred and prior to the resumecontinuation component 116 sending the resume continuation command. Theexecution of the read command and the execution of the program or eraseoperation can occur consecutively to increase bandwidth efficiency ofthe memory component and will not occur in parallel until the autoresume command has been received by the memory device 130. The programor erase operation may not resume without the auto resume command beingsent by the auto resume component 113.

FIG. 2 is a flow diagram of a process 202 to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure. The process 202 can be performed by processing logic thatcan include hardware (e.g., processing device, circuitry, dedicatedlogic, programmable logic, microcode, hardware of a device, integratedcircuit, etc.), software (e.g., instructions run or executed on aprocessing device), or a combination thereof. In some embodiments, theprocess 202 is performed by and/or utilizing the auto resume component113 of FIG. 1. Although shown in a particular sequence or order, unlessotherwise specified, the order of the processes can be modified. Thus,the illustrated embodiments should be understood only as examples, andthe illustrated processes can be performed in a different order, andsome processes can be performed in parallel. Additionally, one or moreprocesses can be omitted in various embodiments. Thus, not all processesare required in every embodiment. Other process flows are possible.

A computing system can include a memory component (e.g. memory device130 of FIG. 1) and a processing device (e.g., controller 115 of FIG. 1),among other components. The memory component can include a read buffer,a write buffer, a memory array 222, and/or an input/output (I/O) device221.

In process 202, a program or erase operation can be suspended while aread command 223 is sent from the processing device to array 222 via theI/O device 221. The read command can be received by the memory array 222and executed 224. For example, data 225 can be read from array 222 andsent to the processing device via the I/O device 221. However, thesuspended program or erase operation does not automatically resume afterexecution 224 of the read command. Further, although not shown in FIG.2, multiple read commands can be sent from the processing device to thememory array 222 for execution in a similar manner.

To restore the program or erase operation from its suspended state, anauto resume command 226 can be sent to memory array 222 from theprocessing device via I/O device 221 prior to sending the last readcommand 227. The auto resume command 226 can signal the array 222 suchthat the array can automatically resume execution of the suspendedprogram or erase operation after the last read command has been executed228. The memory array 222 can execute 228 the last read command and sendthe read data 237 back to the processing device via I/O device 221.Execution of the suspended program or erase operation can then beresumed 229 by the memory array 222 after executing the last readcommand. For instance, the execution of the suspended program or eraseoperation may only be resumed after executing 228 the last read command227 that was sent after sending the auto resume command 226. Further,the execution of the suspended program or erase operation can be resumed229 while the read data 237 is being sent to the processing device viaI/O device 221.

FIG. 3 is a flow diagram of a process 333 to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure The process 333 can be performed by processing logic that caninclude hardware (e.g., processing device, circuitry, dedicated logic,programmable logic, microcode, hardware of a device, integrated circuit,etc.), software (e.g., instructions run or executed on a processingdevice), or a combination thereof. In some embodiments, the process 333is performed by and/or utilizing the auto resume component 113 ofFIG. 1. Although shown in a particular sequence or order, unlessotherwise specified, the order of the processes can be modified. Thus,the illustrated embodiments should be understood only as examples, andthe illustrated processes can be performed in a different order, andsome processes can be performed in parallel. Additionally, one or moreprocesses can be omitted in various embodiments. Thus, not all processesare required in every embodiment. Other process flows are possible.

As shown in FIG. 3, the process 333 can involve an input/output (I/O)device 341 which can be analogous to input/output (I/O) device 221illustrated in FIG. 2. The process 333 can also involve a memory array342, which can be analogous to memory array 222 of FIG. 2.

In process 341, a program or erase operation can be suspended while aread command 343 is sent from the processing device to memory array 342via the I/O device 341. The read command can be received by the memoryarray 342 and executed 344. For example, data 345 can be read from array342 and sent to the processing device via the I/O device 341. However,the suspended program or erase operation does not automatically resumeafter execution 344 of the read command. Further, although not shown inFIG. 2, multiple read commands can be sent via the I/O device 341 to thememory array 342 for execution in a similar manner.

To restore the program or erase operation from its suspended state, anauto resume command 347 can be sent to memory array 342 via I/O device341 after the last read command 346 has been sent to the memory array342. The auto resume command 347 can signal the array 342 toautomatically resume execution of the suspended program or eraseoperation after the last read command has been executed 348. The memoryarray 342 can execute 348 the last read command and send the read data334 back to the processing device via I/O device 341. The last readcommand 346 can be executed 348 for a longer time by the memory array342 than if the auto resume command were sent prior to the last readcommand (e.g., as illustrated in FIG. 2) because the last read command346 can begin to be executed immediately after being sent. Further, theauto resume command 347 can be sent to array 342 at any point during theexecution 348 of the last read command. Execution of the suspendedprogram or erase operation can then be resumed 349 by the memory array342 after executing the last read command 346. For instance, theexecution of the suspended program or erase operation may only beresumed after executing 348 the last read command 346 that was sentprior to sending the auto resume command 347. Further, the execution ofthe suspended program or erase operation can be resumed 349 while theread data 334 is being sent to the processing device via I/O device 341.

FIG. 4 is a flow diagram of a process 450 to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure. The process 450 can be performed by processing logic thatcan include hardware (e.g., processing device, circuitry, dedicatedlogic, programmable logic, microcode, hardware of a device, integratedcircuit, etc.), software (e.g., instructions run or executed on aprocessing device), or a combination thereof. In some embodiments, theprocess 450 is performed by and/or utilizing the resume continuationcomponent 116 of FIG. 1. Although shown in a particular sequence ororder, unless otherwise specified, the order of the processes can bemodified. Thus, the illustrated embodiments should be understood only asexamples, and the illustrated processes can be performed in a differentorder, and some processes can be performed in parallel. Additionally,one or more processes can be omitted in various embodiments. Thus, notall processes are required in every embodiment. Other process flows arepossible.

As shown in FIG. 4, the process 450 can involve an input/output (I/O)device 451 which can be analogous to I/O device 221 and I/O device 341illustrated in FIG. 2 and FIG. 3 respectively. The process 450 can alsoinvolve memory array 452, which can be analogous to memory array 222 andmemory array 342 of FIG. 2 and FIG. 3 respectively.

A computing system can include a memory component (e.g., memory device130 of FIG. 1) and a processing device (e.g., controller 115 of FIG. 1),among other components. The memory component can, can include a readbuffer, a write buffer, a memory array 452, and/or an input/output (I/O)device 451.

In process 450, a program or erase operation can be suspended while aread command 454 is sent from the processing device to memory array 452via the I/O device 451. An auto resume command 453 can accompany thelast read command 454 to the memory array 452. The auto resume command453 can be sent with (e.g., accompany) the read command 454 sent to thememory array 452. The auto resume command 453 can signal the memoryarray 452 to automatically resume execution of the suspended program orerase operation after read command 454 has been executed 455. The readcommand 454 can be sent by the I/O device 451 to be executed. The memoryarray 452 can execute 455 the read command 454 and send the read data456 back to the processing device via I/O device 451. As illustrated inFIG. 4, the auto resume command 453 is sent prior to read command 454.However, embodiments are not so limited and, in another embodiment, theauto resume command 453 can be sent after the read command 454.

Execution of the suspended program or erase operation 457-1 can betemporarily resumed by the memory array 452 after the read command 454has been executed 455 and while the read data 456 is being sent to theprocessing device via I/O device 451. A resume continuation command 458can be sent from the processing device to memory array 452 via I/Odevice 451 after the read data 456 has been sent to the processingdevice. As such, the execution 455 of the read command 454 and theexecution of the program or erase operation 457-1 occur consecutively,such that both do not occur at the same time.

In process 451, resume continuation command 458 is sent prior to acheckpoint being met. Upon confirming the checkpoint has been met,memory array 452 can continue to execute the program or erase operation457-2. The checkpoint can correspond to a request for page bufferresources by the memory array 452. For instance, the checkpoint cancorrespond to an amount of page buffer resources being used, requested,or to be used. The execution 455 of the read command 454 and theexecution of the program or erase operation 457 occurring consecutivelycan increase efficiency in management of page buffer resources andbandwidth efficiency. For instance, page buffer resources may not beactivated until the checkpoint has been met.

FIG. 5 is a flow diagram of a process 570 to resume program or eraseoperations in memory in accordance with some embodiments of the presentdisclosure. The process 570 can be performed by processing logic thatcan include hardware (e.g., processing device, circuitry, dedicatedlogic, programmable logic, microcode, hardware of a device, integratedcircuit, etc.), software (e.g., instructions run or executed on aprocessing device), or a combination thereof. In some embodiments, theprocess 570 is performed by and/or utilizing the resume continuationcomponent 116 of FIG. 1. Although shown in a particular sequence ororder, unless otherwise specified, the order of the processes can bemodified. Thus, the illustrated embodiments should be understood only asexamples, and the illustrated processes can be performed in a differentorder, and some processes can be performed in parallel. Additionally,one or more processes can be omitted in various embodiments. Thus, notall processes are required in every embodiment. Other process flows arepossible.

As shown in FIG. 5, the process 570 can involve an input/output (I/O)571 which can be analogous to I/O device 221, I/O device 341, and I/Odevice 451 illustrated in FIG. 2, FIG. 3, and FIG. 4 respectively. Theprocess 570 can also involve memory array 572, which can also beanalogous to memory array 222, memory array 342, and memory array 452 ofFIG. 2, FIG. 3, and FIG. 4 respectively.

In process 570, a program or erase operation can be suspended while aread command 574 is sent from the processing device to memory array 572via the I/O device 571. The processing device can send an auto resumecommand 573 along with read command 574 to the memory array 572. Theauto resume command 573 can signal the memory array 572 to automaticallyresume execution of the suspended program or erase operation after readcommand 574 has been executed 575. The read command 574 can be sent bythe I/O device 571 to be executed. The memory array 572 can execute 575the read command 574 and send the read data 576 to the processing devicevia I/O device 571. As illustrated in FIG. 5, the auto resume command573 is sent prior to read command 574. However, embodiments are not solimited and, in another embodiment, the auto resume command 573 can besent after the read command 574.

Execution of the suspended program or erase operation 577-1 can betemporarily resumed by the memory array 572 after the read command 574has been executed 575 and while the read data 576 is being sent to theprocessing device via I/O device 571. A resume continuation command 578can be sent from the processing device to memory array 572 via I/Odevice 571 after the read data 576 has been sent to the processingdevice. For instance, the read data 576 can continue to be sent to theprocessing device until a resume continuation command 578 is received.

In process 570, the resume continuation command 578 is sent after acheckpoint is met. Upon confirming the checkpoint has been met, butbefore receiving the resume continuation command 578, memory array 572can temporarily pause 579 the program or erase operation. The checkpointcan correspond to a request for page buffer resources by the memoryarray 572. For instance, the checkpoint can correspond to an amount ofpage buffer resources being used, requested, or to be used. Once thecheckpoint is met, and the resume continuation command 578 is received,memory array 572 can continue 577-2 the program or erase operation. Thatis, the program or erase operation is only continued 577-2 responsive tomeeting the checkpoint and receiving the resume continuation command578.

FIG. 6 is a flow diagram of an example method 660 to resume program orerase operations in memory in accordance with some embodiments of thepresent disclosure. The method 660 can be performed by processing logicthat can include hardware (e.g., processing device, circuitry, dedicatedlogic, programmable logic, microcode, hardware of a device, integratedcircuit, etc.), software (e.g., instructions run or executed on aprocessing device), or a combination thereof. In some embodiments, themethod 660 is performed by and/or utilizing the resume continuationcomponent 116 of FIG. 1 and/or the resume continuation component 716 ofFIG. 7. Although shown in a particular sequence or order, unlessotherwise specified, the order of the processes can be modified. Thus,the illustrated embodiments should be understood only as examples, andthe illustrated processes can be performed in a different order, andsome processes can be performed in parallel. Additionally, one or moreprocesses can be omitted in various embodiments. Thus, not all processesare required in every embodiment. Other process flows are possible.

At operation 662, a memory component receives a read command while aprogram or erase operation being executed by the memory component issuspended. For instance, a processing device (e.g., the processor 117illustrated in FIG. 1, herein) can send the read command to the memorycomponent. The memory component can receive the read command while aprogram or erase operation is suspended. The received read command doesnot automatically resume the suspended program or erase operation.

At operation 664, the memory component confirms a resume continuationcommand has been received. In one embodiment, the resume continuationcommand can be confirmed after receiving the resume continuationcommand. In another embodiment, the memory component can seek to confirmif the resume continuation command has been received prior to receivingthe resume continuation command. The resume continuation command can besent to the memory component after the execution of a last read command.

At operation 667, the memory component resumes execution of the programor erase operation responsive to confirming the resume continuationcommand has been received and a checkpoint for resuming the program orerase operation has been met. The suspended program or erase operationcan be temporarily resumed by the memory component after the executionof a last read command. A resume continuation command can be received bythe memory component after the execution of the last read command. If aresume continuation command is sent prior to the checkpoint being met,the resumption of the program or erase operation can be continued. Ifthe resume continuation command is sent after the checkpoint is met, theresumption of the program or erase operation would have been temporarilypaused once the checkpoint was met, but can then be continued once theresume continuation command is sent. The checkpoint can correspond to arequest for page buffer resources by the memory array. For instance, thecheckpoint can correspond to an amount of page buffer resources beingused, requested, or to be used. Once the checkpoint is met, and theresume continuation command is confirmed to have been previouslyreceived, the program or erase operation can be resumed. For instance,the program or erase operation may only be resumed responsive to meetingthe checkpoint and receiving the resume continuation command.

FIG. 7 is a block diagram of an example computer system 701 in whichembodiments of the present disclosure can operate. For example, FIG. 7illustrates an example machine of a computer system 701 within which aset of instructions, for causing the machine to perform any one or moreof the methodologies discussed herein, can be executed. In someembodiments, the computer system 701 can correspond to a host system(e.g., the host system 120 of FIG. 1) that includes, is coupled to, orutilizes a memory sub-system (e.g., the memory sub-system 110 of FIG. 1)or can be used to perform the operations of a controller (e.g., toexecute an operating system to perform operations corresponding to theauto resume component 113 and the resume continuation component 116 ofFIG. 1). In alternative embodiments, the machine can be connected (e.g.,networked) to other machines in a LAN, an intranet, an extranet, and/orthe Internet. The machine can operate in the capacity of a server or aclient machine in client-server network environment, as a peer machinein a peer-to-peer (or distributed) network environment, or as a serveror a client machine in a cloud computing infrastructure or environment.

The machine can be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a server, a network router, a switch or bridge, or anymachine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while a single machine is illustrated, the term “machine” shall also betaken to include any collection of machines that individually or jointlyexecute a set (or multiple sets) of instructions to perform any one ormore of the methodologies discussed herein.

The example computer system 701 includes a processing device 702, a mainmemory 704 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc.), a static memory 706 (e.g., flash memory, static randomaccess memory (SRAM), etc.), and a data storage system 718, whichcommunicate with each other via a bus 730.

The processing device 702 represents one or more general-purposeprocessing devices such as a microprocessor, a central processing unit,or the like. More particularly, the processing device can be a complexinstruction set computing (CISC) microprocessor, reduced instruction setcomputing (RISC) microprocessor, very long instruction word (VLIW)microprocessor, or a processor implementing other instruction sets, orprocessors implementing a combination of instruction sets. Theprocessing device 702 can also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor, or the like. The processing device 702 can executeinstructions 726 for performing the operations and steps discussedherein. The computer system 701 can further include a network interfacedevice 708 to communicate over the network 720.

The data storage system 718 can include a machine-readable storagemedium 724 (also known as a computer-readable medium) on which is storedone or more sets of instructions 726 or software embodying any one ormore of the methodologies or functions described herein. Theinstructions 726 can also reside, completely or at least partially,within the main memory 704 and/or within the processing device 702during execution thereof by the computer system 701, the main memory 704and the processing device 702 also constituting machine-readable storagemedia. The machine-readable storage medium 724, data storage system 718,and/or main memory 704 can correspond to the memory sub-system 110 ofFIG. 1.

In one embodiment, the instructions 726 include instructions toimplement functionality corresponding to auto resume component 713 andthe resume continuation component 716. While the machine-readablestorage medium 724 is shown in an example embodiment to be a singlemedium, the term “machine-readable storage medium” should be taken toinclude a single medium or multiple media that store the one or moresets of instructions. The term “machine-readable storage medium” shallalso be taken to include any medium that is capable of storing orencoding a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresent disclosure. The term “machine-readable storage medium” shallaccordingly be taken to include, but not be limited to, solid-statememories, optical media, and magnetic media.

Some portions of the preceding detailed descriptions have been presentedin terms of algorithms and symbolic representations of operations ondata bits within a computer memory. These algorithmic descriptions andrepresentations are the ways used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. The presentdisclosure can refer to the action and processes of a computer system,or similar electronic computing device, that manipulates and transformsdata represented as physical (electronic) quantities within the computersystem's registers and memories into other data similarly represented asphysical quantities within the computer system memories or registers orother such information storage systems.

The present disclosure also relates to an apparatus for performing theoperations herein. This apparatus can be specially constructed for theintended purposes, or it can include a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program can be stored in a computerreadable storage medium, such as, but not limited to, any type of diskincluding floppy disks, optical disks, CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring electronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems can be used with programs in accordance with the teachingsherein, or it can prove convenient to construct a more specializedapparatus to perform the method. The structure for a variety of thesesystems will appear as set forth in the description below. In addition,the present disclosure is not described with reference to any particularprogramming language. It will be appreciated that a variety ofprogramming languages can be used to implement the teachings of thedisclosure as described herein.

The present disclosure can be provided as a computer program product, orsoftware, that can include a machine-readable medium having storedthereon instructions, which can be used to program a computer system (orother electronic devices) to perform a process according to the presentdisclosure. A machine-readable medium includes any mechanism for storinginformation in a form readable by a machine (e.g., a computer). In someembodiments, a machine-readable (e.g., computer-readable) mediumincludes a machine (e.g., a computer) readable storage medium such as aread only memory (“ROM”), random access memory (“RAM”), magnetic diskstorage media, optical storage media, flash memory devices, etc.

In the foregoing specification, embodiments of the disclosure have beendescribed with reference to specific example embodiments thereof. Itwill be evident that various modifications can be made thereto withoutdeparting from the broader spirit and scope of embodiments of thedisclosure as set forth in the following claims. The specification anddrawings are, accordingly, to be regarded in an illustrative senserather than a restrictive sense.

What is claimed is:
 1. A system, comprising: a memory component; aprocessing device, operatively coupled with the memory component, to:send a read command to the memory component while a program or eraseoperation being executed by the memory component is suspended; and sendan auto resume command to the memory component to automatically resumeexecution of the program or erase operation after the read command isexecuted.
 2. The system of claim 1, wherein the auto resume command issent to the memory component before the read command is sent to thememory component.
 3. The system of claim 1, wherein the auto resumecommand is sent to the memory component after the read command is sentto the memory component.
 4. The system of claim 3, wherein the autoresume command sent after the read command is sent any time during theexecution of the read command.
 5. The system of claim 3, wherein theread command is executed for a longer period in the memory componentwhen the auto resume command is sent to the memory component after theread command is sent to the memory component compared to the auto resumecommand being sent to the memory component before the read command issent to the memory component.
 6. The system of claim 1, wherein dataread from the memory component during execution of the read command istransferred to the processing device while the program or eraseoperation has resumed being executed.
 7. The system of claim 1, whereinthe memory component is configured to resume execution of the program orerase operation only after executing the read command upon receiving theauto resume command.
 8. A method, comprising: receiving, by a memorycomponent, a read command while a program or erase operation beingexecuted by the memory component is suspended; confirming, by the memorycomponent, a resume continuation command has been received; andresuming, by the memory component, execution of the program or eraseoperation responsive to confirming the resume continuation command hasbeen received and a checkpoint for resuming the program or eraseoperation being met.
 9. The method of claim 8, further comprisingreceiving, by the memory component, the resume continuation commandprior to confirming the resume continuation command has been received.10. The method of claim 8, further comprising receiving, by the memorycomponent, the resume continuation command subsequent to confirming theresume continuation command has been received.
 11. The method of claim10, further comprising pausing, by the memory component, execution ofthe program or erase operation responsive to the resume continuationcommand being received subsequent to confirming receipt of the resumecontinuation command and the checkpoint for resuming the program orerase operation have not been met.
 12. The method of claim 11, furthercomprising resuming the paused execution of the program or eraseoperation responsive to receiving the resume continuation command. 13.The method of claim 8, further comprising confirming the resumecontinuation command has been received responsive to page bufferresources of the memory component being used.
 14. The method of claim13, further comprising corresponding the checkpoint for resuming theprogram or erase operation to an amount of page buffer resources of thememory component being used.
 15. A non-transitory computer-readablestorage medium comprising instructions that, when executed by aprocessing device, cause the processing device to: send a read commandto a memory component while a program or erase operation being executedby the memory component is suspended; send an auto resume command to thememory component to automatically resume execution of the program orerase operation after the read command is executed; execute the readcommand; send a resume continuation command to the memory componentafter the read command has been executed by the memory component; andresume the execution of the program or erase operation responsive tosending the resume continuation command and a checkpoint for resumingthe program or erase operation being met.
 16. The non-transitorycomputer-readable storage medium of claim 15, wherein the instructions,when executed, cause the processor to temporarily resume the executionof the program or erase operation after execution of the read command,prior to sending the resume continuation command.
 17. The non-transitorycomputer-readable storage medium of claim 16, wherein the instructions,when executed, cause the processor to receive data from the executedread command while the execution of the program or erase operation istemporarily resumed.
 18. The non-transitory computer-readable storagemedium of claim 15, wherein the execution of the program or eraseoperation is not resumed without the auto resume command being sent tothe memory component.
 19. The non-transitory computer-readable storagemedium of claim 15, wherein the execution of the read command and theexecution of the program or erase operation occur consecutively.
 20. Thenon-transitory computer-readable storage medium of claim 19, wherein theexecution of the read command and the execution of the program or eraseoperation occurring parallel increases bandwidth efficiency of thememory component.